Output server logs and handle SIGTERM #68
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
svnserve
has the option--log-file
:--log-file ARG : svnserve log file
I added a
docker-entrypoint.sh
script that creates a named pipe usingmkfifo
, runssvnserve
in the background and then redirects logs from the named pipe to the stdout for Docker. Once a SIGTERM is received, sends the SIGTERM signal to thesvnserve
in the background.I also added the
.gitattributes
file, since I'm on Windows git tries to 'fix' line endings to\r\n
and Docker doesn't like that.And finally, before the container would never terminate gracefully when stopped, it would always be killed after the grace period. Now, the SIGTERM signal should be correctly forwarded to
svnserve
, which closes the named pipe after it's done, which also breaks the while loop terminating the whole entrypoint script.